Agent-assisted discovery of network devices and services

ABSTRACT

A computing system may include persistent storage disposed within a remote network management platform and a proxy software application disposed within a managed network that is associated with the remote network management platform. The proxy software application may be configured to: (i) receive, from the remote network management platform, a discovery request; (ii) determine that the discovery request targets a computing device and is to be performed by way of a software agent deployed on the computing device; (iii) based on the discovery request, generate, by way of query mappings, a query expression; (iv) transmit, to the software agent, the query expression; (v) receive, from the software agent, a query response specifying configuration information related to the computing device; (vi) generate, by way of response mappings, a discovery response representing the configuration information related to the computing device; and (vii) transmit, to the remote network management platform, the discovery response.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 16/292,068, filed Mar. 4, 2019, which is herebyincorporated by reference in its entirety.

BACKGROUND

In practice, management of an enterprise's network may involve gatheringinformation regarding the configuration and operational aspects of thenetwork. For instance, the enterprise might have tools with which tofacilitate discovery of devices, applications, and/or services on itsown network. Such discovery may involve learning that certain devices,applications, and/or services are on the network as a general matterand/or may involve gathering other information about those devices,applications, and/or services. Because enterprises might rely ondiscovery to assist with management of their respective networks,technical improvements to discovery-related tools could provide variousbenefits to enterprises.

SUMMARY

An enterprise might have various types of discovery-related tools. Forexample, the enterprise could deploy software agent(s) on its device(s),and those software agent(s) could provide information related to thosedevice(s) as part of query response(s) to query expression(s) thatrequest the information. In another example, a remote network managementplatform could manage the enterprise's network and could facilitateagentless discovery that does not rely on deployment of specializedsoftware (e.g., a software agent) on device(s). Rather, agentlessdiscovery could involve use of remote access protocols and/or standards(e.g., Simple Network Management Protocol (SNMP)), so as to discoverand/or obtain information about configuration item(s), such as devices,applications, and/or services on the managed network.

In practice, the platform could transmit discovery requests to a proxysoftware application deployed on the managed network, so as to cause theproxy software application to engage in the agentless discovery. Theproxy software application could then provide, to the platform,discovery responses that include information related to such discovery,so that the enterprise has access to this information via the platform.

Generally, there could be various similarities and differences betweenthe various tools at issue. In particular, some tools might have atleast some of the same capabilities as one another. For example,different software agents might be capable of discovering at least someof the same types of devices and/or gathering at least some of the sametypes of information. Similarly, agentless discovery and a givensoftware agent might both be capable of discovering at least some of thesame types of devices and/or gathering at least some of the same typesof information. On the other hand, certain tool(s) might havecapabilities that are different from those of other tool(s). Forexample, a given software agent might be able to discover certain typesof devices that agentless discovery and/or other software agent(s) mightnot be capable of discovering, and vice versa. Other examples are alsopossible.

While it is beneficial for the enterprise to have different tools withvarious capabilities, users might encounter various challenges whenusing those tools. For example, formats of discovery requests andresponses supported by the platform may be different respectively fromquery expressions and responses supported by a given software agent.Also, different software agents may respectively support different queryexpressions and/or responses compared to one another. As a result, auser might need to devote significant time to learn about the respectivecapabilities of each tool, so as to learn how to use and gain therespective benefits of the various tools. And even if the user learnshow to use the various tools, the tools would likely provide separatesets of information in different respective formats, and thus the usermight need to engage in a time-consuming and error-prone process thatcould involve converting information from one format to another,deleting of duplicative information, combining the separate sets ofinformation and/or organizing the information, among others.

The present disclosure relates to improved discovery of configurationitem(s) on a managed network. According to the present disclosure, theproxy software application could effectively translate (i) discoveryrequests from the platform into query expressions supported by asoftware agent and (ii) query responses from the software agent intodiscovery responses supported by the platform. The proxy softwareapplication could provide such translations between the platform and oneor more software agents. In this way, the platform could integrate withsoftware agent(s) deployed on computing device(s) of a managed network,which could help overcome the above-described challenges and could alsoprovide for other benefits.

To facilitate the above-mentioned translations between the platform anda particular software agent, the proxy software application could haveaccess to mapping data associated with the particular software agent.More specifically, the proxy software application could have access toquery mappings between (i) formats of at least some of the discoveryrequests supported by the platform and (ii) at least some of the queryexpressions supported by the particular software agent. Additionally,the proxy software application could have access to response mappingsbetween (i) formats of at least some of the query responses supported bythe particular software agent and (ii) at least some discovery responsessupported by the platform.

Given this, the proxy software application could use the mapping data toenable integration between the platform and the particular softwareagent. For example, the proxy software application could receive adiscovery request from the platform, and could determine that thediscovery request targets a particular computing device and is to beperformed by way of the particular software agent. The proxy softwareapplication could then use the discovery request as basis to generate,by way of the query mappings, a query expression supported by theparticular software agent. In turn, the proxy software applicationtransmit the query expression to the particular software agent and couldreceive, from the particular software agent, a query response specifyingconfiguration information related to the particular computing device.Then, the proxy software application could generate, by way of theresponse mappings, a discovery response that is supported by theplatform and that represents the configuration information related tothe particular computing device. As such, the proxy software applicationcould transmit the discovery response to the platform, so that theplatform could then store, in a database, the configuration informationas configuration item(s) and/or carry out other actions.

Overall, the disclosed approach for integrating the platform with one ormore software agents could have numerous benefits. As an initial matter,an enterprise could utilize the platform to obtain information fromsoftware agent(s) without necessarily needing to learn about the queryexpressions and/or responses respectively supported by each suchsoftware agent, thereby allowing the enterprise to gain the respectivebenefits of the software agent(s) and to seamlessly transition fromusing one software agent for discovery to using another software agentfor discovery. Moreover, the platform could discover configuration itemsor otherwise obtain information that the platform might not be able todiscover or otherwise obtain when engaging in agentless discovery,thereby expanding the scope of what the platform could discover onbehalf of the enterprise's managed network. Other advantages are alsopossible.

Accordingly, a first example embodiment may involve a computing systemincluding persistent storage disposed within a remote network managementplatform associated with a managed network as well as a proxy softwareapplication disposed within the managed network. The persistent storagemay contain representations of discovered configuration items within themanaged network. Also, a software agent may be deployed on a computingdevice of the managed network and may be configured to respond to queryexpressions with query responses specifying configurations of thecomputing device. Further, the proxy software application (i) may beconfigured to cause discovery of configuration items on the computingdevice in response to receiving discovery requests from the remotenetwork management platform, (ii) may have access to query mappingsbetween formats of at least some of the discovery requests and at leastsome of the query expressions, and (iii) may have access to responsemappings between formats of at least some of the query responses and atleast some discovery responses supported by the remote networkmanagement platform.

Yet further, the proxy software application may be configured to:receive, from the remote network management platform, a discoveryrequest; determine that the discovery request targets the computingdevice and is to be performed by way of the software agent; based on thediscovery request, generate, by way of the query mappings, a queryexpression; transmit, to the software agent, the query expression;receive, from the software agent, a query response specifyingconfiguration information related to the computing device; generate, byway of the response mappings, a discovery response representing theconfiguration information related to the computing device; and transmit,to the remote network management platform, the discovery response.

A second example embodiment may involve receiving, by a proxy softwareapplication from a remote network management platform, a discoveryrequest, where the remote network management platform is associated witha managed network, where persistent storage is disposed within a remotenetwork management platform, where the persistent storage containsrepresentations of discovered configuration items within the managednetwork, where a software agent is deployed on a computing device of themanaged network and configured to respond to query expressions withquery responses specifying configurations of the computing device, wherethe proxy software application is disposed within the managed network,and wherein the proxy software application (i) is configured to causediscovery of configuration items on the computing device in response toreceiving discovery requests from the remote network managementplatform, (ii) has access to query mappings between formats of at leastsome of the discovery requests and at least some of the queryexpressions, and (iii) has access to response mappings between formatsof at least some of the query responses and at least some discoveryresponses supported by the remote network management platform.

The second example embodiment may also involve determining, the proxysoftware application, that the discovery request targets the computingdevice and is to be performed by way of the software agent. The secondexample embodiment may additionally involve, based on the discoveryrequest, generating, by the proxy software application and using thequery mappings, a query expression. The second example embodiment mayfurther involve transmitting, by the proxy software application to thesoftware agent, the query expression. The second example embodiment mayyet further involve receiving, by the proxy software application fromthe software agent, a query response specifying configurationinformation related to the computing device. The second exampleembodiment may yet further involve generating, by the proxy softwareapplication and using the response mappings, a discovery responserepresenting the configuration information related to the computingdevice. The second example embodiment may yet further involvetransmitting, by the proxy software application to the remote networkmanagement platform, the discovery response.

In a third example embodiment, an article of manufacture may include anon-transitory computer-readable medium, having stored thereon programinstructions that, upon execution by a computing system, cause thecomputing system to perform operations in accordance with the firstand/or second example embodiments.

In a fourth example embodiment, a computing system may include at leastone processor, as well as memory and program instructions. The programinstructions may be stored in the memory, and upon execution by the atleast one processor, cause the computing system to perform operations inaccordance with the first and/or second example embodiments.

In a fifth example embodiment, a system may include various means forcarrying out each of the operations of the first and/or second exampleembodiments.

These, as well as other embodiments, aspects, advantages, andalternatives, will become apparent to those of ordinary skill in the artby reading the following detailed description, with reference whereappropriate to the accompanying drawings. Further, this summary andother descriptions and figures provided herein are intended toillustrate embodiments by way of example only and, as such, thatnumerous variations are possible. For instance, structural elements andprocess steps can be rearranged, combined, distributed, eliminated, orotherwise changed, while remaining within the scope of the embodimentsas claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a schematic drawing of a computing device, inaccordance with example embodiments.

FIG. 2 illustrates a schematic drawing of a server device cluster, inaccordance with example embodiments.

FIG. 3 depicts a remote network management architecture, in accordancewith example embodiments.

FIG. 4 depicts a communication environment involving a remote networkmanagement architecture, in accordance with example embodiments.

FIG. 5A depicts another communication environment involving a remotenetwork management architecture, in accordance with example embodiments.

FIG. 5B is a flow chart, in accordance with example embodiments.

FIG. 6 depicts communications between a remote network managementplatform, a proxy software application, and a software agent, inaccordance with example embodiments.

FIG. 7 is another flow chart, in accordance with example embodiments.

DETAILED DESCRIPTION

Example methods, devices, and systems are described herein. It should beunderstood that the words “example” and “exemplary” are used herein tomean “serving as an example, instance, or illustration.” Any embodimentor feature described herein as being an “example” or “exemplary” is notnecessarily to be construed as preferred or advantageous over otherembodiments or features unless stated as such. Thus, other embodimentscan be utilized and other changes can be made without departing from thescope of the subject matter presented herein.

Accordingly, the example embodiments described herein are not meant tobe limiting. It will be readily understood that the aspects of thepresent disclosure, as generally described herein, and illustrated inthe figures, can be arranged, substituted, combined, separated, anddesigned in a wide variety of different configurations. For example, theseparation of features into “client” and “server” components may occurin a number of ways.

Further, unless context suggests otherwise, the features illustrated ineach of the figures may be used in combination with one another. Thus,the figures should be generally viewed as component aspects of one ormore overall embodiments, with the understanding that not allillustrated features are necessary for each embodiment.

Additionally, any enumeration of elements, blocks, or steps in thisspecification or the claims is for purposes of clarity. Thus, suchenumeration should not be interpreted to require or imply that theseelements, blocks, or steps adhere to a particular arrangement or arecarried out in a particular order.

I. Introduction

A large enterprise is a complex entity with many interrelatedoperations. Some of these are found across the enterprise, such as humanresources (HR), supply chain, information technology (IT), and finance.However, each enterprise also has its own unique operations that provideessential capabilities and/or create competitive advantages.

To support widely-implemented operations, enterprises typically useoff-the-shelf software applications, such as customer relationshipmanagement (CRM) and human capital management (HCM) packages. However,they may also need custom software applications to meet their own uniquerequirements. A large enterprise often has dozens or hundreds of thesecustom software applications. Nonetheless, the advantages provided bythe embodiments herein are not limited to large enterprises and may beapplicable to an enterprise, or any other type of organization, of anysize.

Many such software applications are developed by individual departmentswithin the enterprise. These range from simple spreadsheets tocustom-built software tools and databases. But the proliferation ofsiloed custom software applications has numerous disadvantages. Itnegatively impacts an enterprise's ability to run and grow itsoperations, innovate, and meet regulatory requirements. The enterprisemay find it difficult to integrate, streamline and enhance itsoperations due to lack of a single system that unifies its subsystemsand data.

To efficiently create custom applications, enterprises would benefitfrom a remotely-hosted application platform that eliminates unnecessarydevelopment complexity. The goal of such a platform would be to reducetime-consuming, repetitive application development tasks so thatsoftware engineers and individuals in other roles can focus ondeveloping unique, high-value features.

In order to achieve this goal, the concept of Application Platform as aService (aPaaS) is introduced, to intelligently automate workflowsthroughout the enterprise. An aPaaS system is hosted remotely from theenterprise, but may access data, applications, and services within theenterprise by way of secure connections. Such an aPaaS system may have anumber of advantageous capabilities and characteristics. Theseadvantages and characteristics may be able to improve the enterprise'soperations and workflow for IT, HR, CRM, customer service, applicationdevelopment, and security.

The aPaaS system may support development and execution ofmodel-view-controller (MVC) applications. MVC applications divide theirfunctionality into three interconnected parts (model, view, andcontroller) in order to isolate representations of information from themanner in which the information is presented to the user, therebyallowing for efficient code reuse and parallel development. Theseapplications may be web-based, and offer create, read, update, delete(CRUD) capabilities. This allows new applications to be built on acommon application infrastructure.

The aPaaS system may support standardized application components, suchas a standardized set of widgets for graphical user interface (GUI)development. In this way, applications built using the aPaaS system havea common look and feel. Other software components and modules may bestandardized as well. In some cases, this look and feel can be brandedor skinned with an enterprise's custom logos and/or color schemes.

The aPaaS system may support the ability to configure the behavior ofapplications using metadata. This allows application behaviors to berapidly adapted to meet specific needs. Such an approach reducesdevelopment time and increases flexibility. Further, the aPaaS systemmay support GUI tools that facilitate metadata creation and management,thus reducing errors in the metadata.

The aPaaS system may support clearly-defined interfaces betweenapplications, so that software developers can avoid unwantedinter-application dependencies. Thus, the aPaaS system may implement aservice layer in which persistent state information and other data arestored.

The aPaaS system may support a rich set of integration features so thatthe applications thereon can interact with legacy applications andthird-party applications. For instance, the aPaaS system may support acustom employee-onboarding system that integrates with legacy HR, IT,and accounting systems.

The aPaaS system may support enterprise-grade security. Furthermore,since the aPaaS system may be remotely hosted, it should also utilizesecurity procedures when it interacts with systems in the enterprise orthird-party networks and services hosted outside of the enterprise. Forexample, the aPaaS system may be configured to share data amongst theenterprise and other parties to detect and identify common securitythreats.

Other features, functionality, and advantages of an aPaaS system mayexist. This description is for purpose of example and is not intended tobe limiting.

As an example of the aPaaS development process, a software developer maybe tasked to create a new application using the aPaaS system. First, thedeveloper may define the data model, which specifies the types of datathat the application uses and the relationships therebetween. Then, viaa GUI of the aPaaS system, the developer enters (e.g., uploads) the datamodel. The aPaaS system automatically creates all of the correspondingdatabase tables, fields, and relationships, which can then be accessedvia an object-oriented services layer.

In addition, the aPaaS system can also build a fully-functional MVCapplication with client-side interfaces and server-side CRUD logic. Thisgenerated application may serve as the basis of further development forthe user. Advantageously, the developer does not have to spend a largeamount of time on basic application functionality. Further, since theapplication may be web-based, it can be accessed from anyInternet-enabled client device. Alternatively or additionally, a localcopy of the application may be able to be accessed, for instance, whenInternet service is not available.

The aPaaS system may also support a rich set of pre-definedfunctionality that can be added to applications. These features includesupport for searching, email, templating, workflow design, reporting,analytics, social media, scripting, mobile-friendly output, andcustomized GUIs.

The following embodiments describe architectural and functional aspectsof example aPaaS systems, as well as the features and advantagesthereof.

II. Example Computing Devices and Cloud-Based Computing Environments

FIG. 1 is a simplified block diagram exemplifying a computing device100, illustrating some of the components that could be included in acomputing device arranged to operate in accordance with the embodimentsherein. Computing device 100 could be a client device (e.g., a deviceactively operated by a user), a server device (e.g., a device thatprovides computational services to client devices), or some other typeof computational platform. Some server devices may operate as clientdevices from time to time in order to perform particular operations, andsome client devices may incorporate server features.

In this example, computing device 100 includes processor 102, memory104, network interface 106, and an input/output unit 108, all of whichmay be coupled by a system bus 110 or a similar mechanism. In someembodiments, computing device 100 may include other components and/orperipheral devices (e.g., detachable storage, printers, and so on).

Processor 102 may be one or more of any type of computer processingelement, such as a central processing unit (CPU), a co-processor (e.g.,a mathematics, graphics, or encryption co-processor), a digital signalprocessor (DSP), a network processor, and/or a form of integratedcircuit or controller that performs processor operations. In some cases,processor 102 may be one or more single-core processors. In other cases,processor 102 may be one or more multi-core processors with multipleindependent processing units. Processor 102 may also include registermemory for temporarily storing instructions being executed and relateddata, as well as cache memory for temporarily storing recently-usedinstructions and data.

Memory 104 may be any form of computer-usable memory, including but notlimited to random access memory (RAM), read-only memory (ROM), andnon-volatile memory (e.g., flash memory, hard disk drives, solid statedrives, compact discs (CDs), digital video discs (DVDs), and/or tapestorage). Thus, memory 104 represents both main memory units, as well aslong-term storage. Other types of memory may include biological memory.

Memory 104 may store program instructions and/or data on which programinstructions may operate. By way of example, memory 104 may store theseprogram instructions on a non-transitory, computer-readable medium, suchthat the instructions are executable by processor 102 to carry out anyof the methods, processes, or operations disclosed in this specificationor the accompanying drawings.

As shown in FIG. 1, memory 104 may include firmware 104A, kernel 104B,and/or applications 104C. Firmware 104A may be program code used to bootor otherwise initiate some or all of computing device 100. Kernel 104Bmay be an operating system, including modules for memory management,scheduling and management of processes, input/output, and communication.Kernel 104B may also include device drivers that allow the operatingsystem to communicate with the hardware modules (e.g., memory units,networking interfaces, ports, and busses), of computing device 100.Applications 104C may be one or more user-space software programs, suchas web browsers or email clients, as well as any software libraries usedby these programs. Memory 104 may also store data used by these andother programs and applications.

Network interface 106 may take the form of one or more wirelineinterfaces, such as Ethernet (e.g., Fast Ethernet, Gigabit Ethernet, andso on). Network interface 106 may also support communication over one ormore non-Ethernet media, such as coaxial cables or power lines, or overwide-area media, such as Synchronous Optical Networking (SONET) ordigital subscriber line (DSL) technologies. Network interface 106 mayadditionally take the form of one or more wireless interfaces, such asIEEE 802.11 (Wifi), BLUETOOTH®, global positioning system (GPS), or awide-area wireless interface. However, other forms of physical layerinterfaces and other types of standard or proprietary communicationprotocols may be used over network interface 106. Furthermore, networkinterface 106 may comprise multiple physical interfaces. For instance,some embodiments of computing device 100 may include Ethernet,BLUETOOTH®, and Wifi interfaces.

Input/output unit 108 may facilitate user and peripheral deviceinteraction with computing device 100. Input/output unit 108 may includeone or more types of input devices, such as a keyboard, a mouse, a touchscreen, and so on. Similarly, input/output unit 108 may include one ormore types of output devices, such as a screen, monitor, printer, and/orone or more light emitting diodes (LEDs). Additionally or alternatively,computing device 100 may communicate with other devices using auniversal serial bus (USB) or high-definition multimedia interface(HDMI) port interface, for example.

In some embodiments, one or more computing devices like computing device100 may be deployed to support an aPaaS architecture. The exact physicallocation, connectivity, and configuration of these computing devices maybe unknown and/or unimportant to client devices. Accordingly, thecomputing devices may be referred to as “cloud-based” devices that maybe housed at various remote data center locations.

FIG. 2 depicts a cloud-based server cluster 200 in accordance withexample embodiments. In FIG. 2, operations of a computing device (e.g.,computing device 100) may be distributed between server devices 202,data storage 204, and routers 206, all of which may be connected bylocal cluster network 208. The number of server devices 202, datastorages 204, and routers 206 in server cluster 200 may depend on thecomputing task(s) and/or applications assigned to server cluster 200.

For example, server devices 202 can be configured to perform variouscomputing tasks of computing device 100. Thus, computing tasks can bedistributed among one or more of server devices 202. To the extent thatthese computing tasks can be performed in parallel, such a distributionof tasks may reduce the total time to complete these tasks and return aresult. For purpose of simplicity, both server cluster 200 andindividual server devices 202 may be referred to as a “server device.”This nomenclature should be understood to imply that one or moredistinct server devices, data storage devices, and cluster routers maybe involved in server device operations.

Data storage 204 may be data storage arrays that include drive arraycontrollers configured to manage read and write access to groups of harddisk drives and/or solid state drives. The drive array controllers,alone or in conjunction with server devices 202, may also be configuredto manage backup or redundant copies of the data stored in data storage204 to protect against drive failures or other types of failures thatprevent one or more of server devices 202 from accessing units of datastorage 204. Other types of memory aside from drives may be used.

Routers 206 may include networking equipment configured to provideinternal and external communications for server cluster 200. Forexample, routers 206 may include one or more packet-switching and/orrouting devices (including switches and/or gateways) configured toprovide (i) network communications between server devices 202 and datastorage 204 via local cluster network 208, and/or (ii) networkcommunications between the server cluster 200 and other devices viacommunication link 210 to network 212.

Additionally, the configuration of routers 206 can be based at least inpart on the data communication requirements of server devices 202 anddata storage 204, the latency and throughput of the local clusternetwork 208, the latency, throughput, and cost of communication link210, and/or other factors that may contribute to the cost, speed,fault-tolerance, resiliency, efficiency and/or other design goals of thesystem architecture.

As a possible example, data storage 204 may include any form ofdatabase, such as a structured query language (SQL) database. Varioustypes of data structures may store the information in such a database,including but not limited to tables, arrays, lists, trees, and tuples.Furthermore, any databases in data storage 204 may be monolithic ordistributed across multiple physical devices.

Server devices 202 may be configured to transmit data to and receivedata from data storage 204. This transmission and retrieval may take theform of SQL queries or other types of database queries, and the outputof such queries, respectively. Additional text, images, video, and/oraudio may be included as well. Furthermore, server devices 202 mayorganize the received data into web page representations. Such arepresentation may take the form of a markup language, such as thehypertext markup language (HTML), the extensible markup language (XML),or some other standardized or proprietary format. Moreover, serverdevices 202 may have the capability of executing various types ofcomputerized scripting languages, such as but not limited to Perl,Python, PHP Hypertext Preprocessor (PHP), Active Server Pages (ASP),JavaScript, and so on. Computer program code written in these languagesmay facilitate the providing of web pages to client devices, as well asclient device interaction with the web pages.

III. Example Remote Network Management Architecture

FIG. 3 depicts a remote network management architecture, in accordancewith example embodiments. This architecture includes three maincomponents, managed network 300, remote network management platform 320,and third-party networks 340, all connected by way of Internet 350.

Managed network 300 may be, for example, an enterprise network used byan entity for computing and communications tasks, as well as storage ofdata. Thus, managed network 300 may include various client devices 302,server devices 304, routers 306, virtual machines 308, firewall 310,and/or proxy servers 312. Client devices 302 may be embodied bycomputing device 100, server devices 304 may be embodied by computingdevice 100 or server cluster 200, and routers 306 may be any type ofrouter, switch, or gateway.

Virtual machines 308 may be embodied by one or more of computing device100 or server cluster 200. In general, a virtual machine is an emulationof a computing system, and mimics the functionality (e.g., processor,memory, and communication resources) of a physical computer. Onephysical computing system, such as server cluster 200, may support up tothousands of individual virtual machines. In some embodiments, virtualmachines 308 may be managed by a centralized server device orapplication that facilitates allocation of physical computing resourcesto individual virtual machines, as well as performance and errorreporting. Enterprises often employ virtual machines in order toallocate computing resources in an efficient, as needed fashion.Providers of virtualized computing systems include VMWARE® andMICROSOFT®.

Firewall 310 may be one or more specialized routers or server devicesthat protect managed network 300 from unauthorized attempts to accessthe devices, applications, and services therein, while allowingauthorized communication that is initiated from managed network 300.Firewall 310 may also provide intrusion detection, web filtering, virusscanning, application-layer gateways, and other applications orservices. In some embodiments not shown in FIG. 3, managed network 300may include one or more virtual private network (VPN) gateways withwhich it communicates with remote network management platform 320 (seebelow).

Managed network 300 may also include one or more proxy servers 312. Anembodiment of proxy servers 312 may be a server device that facilitatescommunication and movement of data between managed network 300, remotenetwork management platform 320, and third-party networks 340. Inparticular, proxy servers 312 may be able to establish and maintainsecure communication sessions with one or more computational instancesof remote network management platform 320. By way of such a session,remote network management platform 320 may be able to discover andmanage aspects of the architecture and configuration of managed network300 and its components. Possibly with the assistance of proxy servers312, remote network management platform 320 may also be able to discoverand manage aspects of third-party networks 340 that are used by managednetwork 300.

Firewalls, such as firewall 310, typically deny all communicationsessions that are incoming by way of Internet 350, unless such a sessionwas ultimately initiated from behind the firewall (i.e., from a deviceon managed network 300) or the firewall has been explicitly configuredto support the session. By placing proxy servers 312 behind firewall 310(e.g., within managed network 300 and protected by firewall 310), proxyservers 312 may be able to initiate these communication sessions throughfirewall 310. Thus, firewall 310 might not have to be specificallyconfigured to support incoming sessions from remote network managementplatform 320, thereby avoiding potential security risks to managednetwork 300.

In some cases, managed network 300 may consist of a few devices and asmall number of networks. In other deployments, managed network 300 mayspan multiple physical locations and include hundreds of networks andhundreds of thousands of devices. Thus, the architecture depicted inFIG. 3 is capable of scaling up or down by orders of magnitude.

Furthermore, depending on the size, architecture, and connectivity ofmanaged network 300, a varying number of proxy servers 312 may bedeployed therein. For example, each one of proxy servers 312 may beresponsible for communicating with remote network management platform320 regarding a portion of managed network 300. Alternatively oradditionally, sets of two or more proxy servers may be assigned to sucha portion of managed network 300 for purposes of load balancing,redundancy, and/or high availability.

Remote network management platform 320 is a hosted environment thatprovides aPaaS services to users, particularly to the operators ofmanaged network 300. These services may take the form of web-basedportals, for instance. Thus, a user can securely access remote networkmanagement platform 320 from, for instance, client devices 302, orpotentially from a client device outside of managed network 300. By wayof the web-based portals, users may design, test, and deployapplications, generate reports, view analytics, and perform other tasks.

As shown in FIG. 3, remote network management platform 320 includes fourcomputational instances 322, 324, 326, and 328. Each of these instancesmay represent one or more server devices and/or one or more databasesthat provide a set of web portals, services, and applications (e.g., awholly-functioning aPaaS system) available to a particular customer. Insome cases, a single customer may use multiple computational instances.For example, managed network 300 may be an enterprise customer of remotenetwork management platform 320, and may use computational instances322, 324, and 326. The reason for providing multiple instances to onecustomer is that the customer may wish to independently develop, test,and deploy its applications and services. Thus, computational instance322 may be dedicated to application development related to managednetwork 300, computational instance 324 may be dedicated to testingthese applications, and computational instance 326 may be dedicated tothe live operation of tested applications and services. A computationalinstance may also be referred to as a hosted instance, a remoteinstance, a customer instance, or by some other designation. Anyapplication deployed onto a computational instance may be a scopedapplication, in that its access to databases within the computationalinstance can be restricted to certain elements therein (e.g., one ormore particular database tables or particular rows with one or moredatabase tables).

For purpose of clarity, the disclosure herein refers to the physicalhardware, software, and arrangement thereof as a “computationalinstance.” Note that users may colloquially refer to the graphical userinterfaces provided thereby as “instances.” But unless it is definedotherwise herein, a “computational instance” is a computing systemdisposed within remote network management platform 320.

The multi-instance architecture of remote network management platform320 is in contrast to conventional multi-tenant architectures, overwhich multi-instance architectures have several advantages. Inmulti-tenant architectures, data from different customers (e.g.,enterprises) are comingled in a single database. While these customers'data are separate from one another, the separation is enforced by thesoftware that operates the single database. As a consequence, a securitybreach in this system may impact all customers' data, creatingadditional risk, especially for entities subject to governmental,healthcare, and/or financial regulation. Furthermore, any databaseoperations that impact one customer will likely impact all customerssharing that database. Thus, if there is an outage due to hardware orsoftware errors, this outage affects all such customers. Likewise, ifthe database is to be upgraded to meet the needs of one customer, itwill be unavailable to all customers during the upgrade process. Often,such maintenance windows will be long, due to the size of the shareddatabase.

In contrast, the multi-instance architecture provides each customer withits own database in a dedicated computing instance. This preventscomingling of customer data, and allows each instance to beindependently managed. For example, when one customer's instanceexperiences an outage due to errors or an upgrade, other computationalinstances are not impacted. Maintenance down time is limited because thedatabase only contains one customer's data. Further, the simpler designof the multi-instance architecture allows redundant copies of eachcustomer database and instance to be deployed in a geographicallydiverse fashion. This facilitates high availability, where the liveversion of the customer's instance can be moved when faults are detectedor maintenance is being performed.

In some embodiments, remote network management platform 320 may includeone or more central instances, controlled by the entity that operatesthis platform. Like a computational instance, a central instance mayinclude some number of physical or virtual servers and database devices.Such a central instance may serve as a repository for data that can beshared amongst at least some of the computational instances. Forinstance, definitions of common security threats that could occur on thecomputational instances, software packages that are commonly discoveredon the computational instances, and/or an application store forapplications that can be deployed to the computational instances mayreside in a central instance. Computational instances may communicatewith central instances by way of well-defined interfaces in order toobtain this data.

In order to support multiple computational instances in an efficientfashion, remote network management platform 320 may implement aplurality of these instances on a single hardware platform. For example,when the aPaaS system is implemented on a server cluster such as servercluster 200, it may operate a virtual machine that dedicates varyingamounts of computational, storage, and communication resources toinstances. But full virtualization of server cluster 200 might not benecessary, and other mechanisms may be used to separate instances. Insome examples, each instance may have a dedicated account and one ormore dedicated databases on server cluster 200. Alternatively,computational instance 322 may span multiple physical devices.

In some cases, a single server cluster of remote network managementplatform 320 may support multiple independent enterprises. Furthermore,as described below, remote network management platform 320 may includemultiple server clusters deployed in geographically diverse data centersin order to facilitate load balancing, redundancy, and/or highavailability.

Third-party networks 340 may be remote server devices (e.g., a pluralityof server clusters such as server cluster 200) that can be used foroutsourced computational, data storage, communication, and servicehosting operations. These servers may be virtualized (i.e., the serversmay be virtual machines). Examples of third-party networks 340 mayinclude AMAZON WEB SERVICES® and MICROSOFT® AZURE®. Like remote networkmanagement platform 320, multiple server clusters supporting third-partynetworks 340 may be deployed at geographically diverse locations forpurposes of load balancing, redundancy, and/or high availability.

Managed network 300 may use one or more of third-party networks 340 todeploy applications and services to its clients and customers. Forinstance, if managed network 300 provides online music streamingservices, third-party networks 340 may store the music files and provideweb interface and streaming capabilities. In this way, the enterprise ofmanaged network 300 does not have to build and maintain its own serversfor these operations.

Remote network management platform 320 may include modules thatintegrate with third-party networks 340 to expose virtual machines andmanaged services therein to managed network 300. The modules may allowusers to request virtual resources and provide flexible reporting forthird-party networks 340. In order to establish this functionality, auser from managed network 300 might first establish an account withthird-party networks 340, and request a set of associated resources.Then, the user may enter the account information into the appropriatemodules of remote network management platform 320. These modules maythen automatically discover the manageable resources in the account, andalso provide reports related to usage, performance, and billing.

Internet 350 may represent a portion of the global Internet. However,Internet 350 may alternatively represent a different type of network,such as a private wide-area or local-area packet-switched network.

FIG. 4 further illustrates the communication environment between managednetwork 300 and computational instance 322, and introduces additionalfeatures and alternative embodiments. In FIG. 4, computational instance322 is replicated across data centers 400A and 400B. These data centersmay be geographically distant from one another, perhaps in differentcities or different countries. Each data center includes supportequipment that facilitates communication with managed network 300, aswell as remote users.

In data center 400A, network traffic to and from external devices flowseither through VPN gateway 402A or firewall 404A. VPN gateway 402A maybe peered with VPN gateway 412 of managed network 300 by way of asecurity protocol such as Internet Protocol Security (IPSEC) orTransport Layer Security (TLS). Firewall 404A may be configured to allowaccess from authorized users, such as user 414 and remote user 416, andto deny access to unauthorized users. By way of firewall 404A, theseusers may access computational instance 322, and possibly othercomputational instances. Load balancer 406A may be used to distributetraffic amongst one or more physical or virtual server devices that hostcomputational instance 322. Load balancer 406A may simplify user accessby hiding the internal configuration of data center 400A, (e.g.,computational instance 322) from client devices. For instance, ifcomputational instance 322 includes multiple physical or virtualcomputing devices that share access to multiple databases, load balancer406A may distribute network traffic and processing tasks across thesecomputing devices and databases so that no one computing device ordatabase is significantly busier than the others. In some embodiments,computational instance 322 may include VPN gateway 402A, firewall 404A,and load balancer 406A.

Data center 400B may include its own versions of the components in datacenter 400A. Thus, VPN gateway 402B, firewall 404B, and load balancer406B may perform the same or similar operations as VPN gateway 402A,firewall 404A, and load balancer 406A, respectively. Further, by way ofreal-time or near-real-time database replication and/or otheroperations, computational instance 322 may exist simultaneously in datacenters 400A and 400B.

Data centers 400A and 400B as shown in FIG. 4 may facilitate redundancyand high availability. In the configuration of FIG. 4, data center 400Ais active and data center 400B is passive. Thus, data center 400A isserving all traffic to and from managed network 300, while the versionof computational instance 322 in data center 400B is being updated innear-real-time. Other configurations, such as one in which both datacenters are active, may be supported.

Should data center 400A fail in some fashion or otherwise becomeunavailable to users, data center 400B can take over as the active datacenter. For example, domain name system (DNS) servers that associate adomain name of computational instance 322 with one or more InternetProtocol (IP) addresses of data center 400A may re-associate the domainname with one or more IP addresses of data center 400B. After thisre-association completes (which may take less than one second or severalseconds), users may access computational instance 322 by way of datacenter 400B.

FIG. 4 also illustrates a possible configuration of managed network 300.As noted above, proxy servers 312 and user 414 may access computationalinstance 322 through firewall 310. Proxy servers 312 may also accessconfiguration items 410. In FIG. 4, configuration items 410 may refer toany or all of client devices 302, server devices 304, routers 306, andvirtual machines 308, any applications or services executing thereon, aswell as relationships between devices, applications, and services. Thus,the term “configuration items” may be shorthand for any physical orvirtual device, or any application or service remotely discoverable ormanaged by computational instance 322, or relationships betweendiscovered devices, applications, and services. Configuration items maybe represented in a configuration management database (CMDB) ofcomputational instance 322.

As noted above, VPN gateway 412 may provide a dedicated VPN to VPNgateway 402A. Such a VPN may be helpful when there is a significantamount of traffic between managed network 300 and computational instance322, or security policies otherwise suggest or require use of a VPNbetween these sites. In some embodiments, any device in managed network300 and/or computational instance 322 that directly communicates via theVPN is assigned a public IP address. Other devices in managed network300 and/or computational instance 322 may be assigned private IPaddresses (e.g., IP addresses selected from the 10.0.0.0-10.255.255.255or 192.168.0.0-192.168.255.255 ranges, represented in shorthand assubnets 10.0.0.0/8 and 192.168.0.0/16, respectively).

IV. Example Device, Application, and Service Discovery

In order for remote network management platform 320 to administer thedevices, applications, and services of managed network 300, remotenetwork management platform 320 may first determine what devices arepresent in managed network 300, the configurations and operationalstatuses of these devices, and the applications and services provided bythe devices, and well as the relationships between discovered devices,applications, and services. As noted above, each device, application,service, and relationship may be referred to as a configuration item.The process of defining configuration items within managed network 300is referred to as discovery, and may be facilitated at least in part byproxy servers 312.

For purpose of the embodiments herein, an “application” may refer to oneor more processes, threads, programs, client modules, server modules, orany other software that executes on a device or group of devices. A“service” may refer to a high-level capability provided by multipleapplications executing on one or more devices working in conjunctionwith one another. For example, a high-level web service may involvemultiple web application server threads executing on one device andaccessing information from a database application that executes onanother device.

FIG. 5A provides a logical depiction of how configuration items can bediscovered, as well as how information related to discoveredconfiguration items can be stored. For sake of simplicity, remotenetwork management platform 320, third-party networks 340, and Internet350 are not shown.

In FIG. 5A, CMDB 500 and task list 502 are stored within computationalinstance 322. Computational instance 322 may transmit discovery commandsto proxy servers 312. In response, proxy servers 312 may transmit probesto various devices, applications, and services in managed network 300.These devices, applications, and services may transmit responses toproxy servers 312, and proxy servers 312 may then provide informationregarding discovered configuration items to CMDB 500 for storagetherein. Configuration items stored in CMDB 500 represent theenvironment of managed network 300.

Task list 502 represents a list of activities that proxy servers 312 areto perform on behalf of computational instance 322. As discovery takesplace, task list 502 is populated. Proxy servers 312 repeatedly querytask list 502, obtain the next task therein, and perform this task untiltask list 502 is empty or another stopping condition has been reached.

To facilitate discovery, proxy servers 312 may be configured withinformation regarding one or more subnets in managed network 300 thatare reachable by way of proxy servers 312. For instance, proxy servers312 may be given the IP address range 192.168.0/24 as a subnet. Then,computational instance 322 may store this information in CMDB 500 andplace tasks in task list 502 for discovery of devices at each of theseaddresses.

FIG. 5A also depicts devices, applications, and services in managednetwork 300 as configuration items 504, 506, 508, 510, and 512. As notedabove, these configuration items represent a set of physical and/orvirtual devices (e.g., client devices, server devices, routers, orvirtual machines), applications executing thereon (e.g., web servers,email servers, databases, or storage arrays), relationshipstherebetween, as well as services that involve multiple individualconfiguration items.

Placing the tasks in task list 502 may trigger or otherwise cause proxyservers 312 to begin discovery. Alternatively or additionally, discoverymay be manually triggered or automatically triggered based on triggeringevents (e.g., discovery may automatically begin once per day at aparticular time).

In general, discovery may proceed in four logical phases: scanning,classification, identification, and exploration. Each phase of discoveryinvolves various types of probe messages being transmitted by proxyservers 312 to one or more devices in managed network 300. The responsesto these probes may be received and processed by proxy servers 312, andrepresentations thereof may be transmitted to CMDB 500. Thus, each phasecan result in more configuration items being discovered and stored inCMDB 500.

In the scanning phase, proxy servers 312 may probe each IP address inthe specified range of IP addresses for open Transmission ControlProtocol (TCP) and/or User Datagram Protocol (UDP) ports to determinethe general type of device. The presence of such open ports at an IPaddress may indicate that a particular application is operating on thedevice that is assigned the IP address, which in turn may identify theoperating system used by the device. For example, if TCP port 135 isopen, then the device is likely executing a WINDOWS® operating system.Similarly, if TCP port 22 is open, then the device is likely executing aUNIX® operating system, such as LINUX®. If UDP port 161 is open, thenthe device may be able to be further identified through the SimpleNetwork Management Protocol (SNMP). Other possibilities exist. Once thepresence of a device at a particular IP address and its open ports havebeen discovered, these configuration items are saved in CMDB 500.

In the classification phase, proxy servers 312 may further probe eachdiscovered device to determine the version of its operating system. Theprobes used for a particular device are based on information gatheredabout the devices during the scanning phase. For example, if a device isfound with TCP port 22 open, a set of UNIX®-specific probes may be used.Likewise, if a device is found with TCP port 135 open, a set ofWINDOWS®-specific probes may be used. For either case, an appropriateset of tasks may be placed in task list 502 for proxy servers 312 tocarry out. These tasks may result in proxy servers 312 logging on, orotherwise accessing information from the particular device. Forinstance, if TCP port 22 is open, proxy servers 312 may be instructed toinitiate a Secure Shell (SSH) connection to the particular device andobtain information about the operating system thereon from particularlocations in the file system. Based on this information, the operatingsystem may be determined. As an example, a UNIX® device with TCP port 22open may be classified as AIX®, HPUX, LINUX®, MACOS®, or SOLARIS®. Thisclassification information may be stored as one or more configurationitems in CMDB 500.

In the identification phase, proxy servers 312 may determine specificdetails about a classified device. The probes used during this phase maybe based on information gathered about the particular devices during theclassification phase. For example, if a device was classified as LINUX®,a set of LINUX®-specific probes may be used. Likewise, if a device wasclassified as WINDOWS® 2012, as a set of WINDOWS®-2012-specific probesmay be used. As was the case for the classification phase, anappropriate set of tasks may be placed in task list 502 for proxyservers 312 to carry out. These tasks may result in proxy servers 312reading information from the particular device, such as basicinput/output system (BIOS) information, serial numbers, networkinterface information, media access control address(es) assigned tothese network interface(s), IP address(es) used by the particular deviceand so on. This identification information may be stored as one or moreconfiguration items in CMDB 500.

In the exploration phase, proxy servers 312 may determine furtherdetails about the operational state of a classified device. The probesused during this phase may be based on information gathered about theparticular devices during the classification phase and/or theidentification phase. Again, an appropriate set of tasks may be placedin task list 502 for proxy servers 312 to carry out. These tasks mayresult in proxy servers 312 reading additional information from theparticular device, such as processor information, memory information,lists of running processes (applications), and so on. Once more, thediscovered information may be stored as one or more configuration itemsin CMDB 500.

Running discovery on a network device, such as a router, may utilizeSNMP. Instead of or in addition to determining a list of runningprocesses or other application-related information, discovery maydetermine additional subnets known to the router and the operationalstate of the router's network interfaces (e.g., active, inactive, queuelength, number of packets dropped, etc.). The IP addresses of theadditional subnets may be candidates for further discovery procedures.Thus, discovery may progress iteratively or recursively.

Once discovery completes, a snapshot representation of each discovereddevice, application, and service is available in CMDB 500. For example,after discovery, operating system version, hardware configuration andnetwork configuration details for client devices, server devices, androuters in managed network 300, as well as applications executingthereon, may be stored. This collected information may be presented to auser in various ways to allow the user to view the hardware compositionand operational status of devices, as well as the characteristics ofservices that span multiple devices and applications.

Furthermore, CMDB 500 may include entries regarding dependencies andrelationships between configuration items. More specifically, anapplication that is executing on a particular server device, as well asthe services that rely on this application, may be represented as suchin CMDB 500. For instance, suppose that a database application isexecuting on a server device, and that this database application is usedby a new employee onboarding service as well as a payroll service. Thus,if the server device is taken out of operation for maintenance, it isclear that the employee onboarding service and payroll service will beimpacted. Likewise, the dependencies and relationships betweenconfiguration items may be able to represent the services impacted whena particular router fails.

In general, dependencies and relationships between configuration itemsmay be displayed on a web-based interface and represented in ahierarchical fashion. Thus, adding, changing, or removing suchdependencies and relationships may be accomplished by way of thisinterface.

Furthermore, users from managed network 300 may develop workflows thatallow certain coordinated activities to take place across multiplediscovered devices. For instance, an IT workflow might allow the user tochange the common administrator password to all discovered LINUX®devices in a single operation.

In order for discovery to take place in the manner described above,proxy servers 312, CMDB 500, and/or one or more credential stores may beconfigured with credentials for one or more of the devices to bediscovered. Credentials may include any type of information needed inorder to access the devices. These may include userid/password pairs,certificates, and so on. In some embodiments, these credentials may bestored in encrypted fields of CMDB 500. Proxy servers 312 may containthe decryption key for the credentials so that proxy servers 312 can usethese credentials to log on to or otherwise access devices beingdiscovered.

The discovery process is depicted as a flow chart in FIG. 5B. At block520, the task list in the computational instance is populated, forinstance, with a range of IP addresses. At block 522, the scanning phasetakes place. Thus, the proxy servers probe the IP addresses for devicesusing these IP addresses, and attempt to determine the operating systemsthat are executing on these devices. At block 524, the classificationphase takes place. The proxy servers attempt to determine the operatingsystem version of the discovered devices. At block 526, theidentification phase takes place. The proxy servers attempt to determinethe hardware and/or software configuration of the discovered devices. Atblock 528, the exploration phase takes place. The proxy servers attemptto determine the operational state and applications executing on thediscovered devices. At block 530, further editing of the configurationitems representing the discovered devices and applications may takeplace. This editing may be automated and/or manual in nature.

The blocks represented in FIG. 5B are for purpose of example. Discoverymay be a highly configurable procedure that can have more or fewerphases, and the operations of each phase may vary. In some cases, one ormore phases may be customized, or may otherwise deviate from theexemplary descriptions above.

V. CMDB Identification Rules and Reconciliation

A CMDB, such as CMDB 500, provides a repository of configuration items,and when properly provisioned, can take on a key role in higher-layerapplications deployed within or involving a computational instance.These applications may relate to enterprise IT service management,operations management, asset management, configuration management,compliance, and so on.

For example, an IT service management application may use information inthe CMDB to determine applications and services that may be impacted bya component (e.g., a server device) that has malfunctioned, crashed, oris heavily loaded. Likewise, an asset management application may useinformation in the CMDB to determine which hardware and/or softwarecomponents are being used to support particular enterprise applications.As a consequence of the importance of the CMDB, it is desirable for theinformation stored therein to be accurate, consistent, and up to date.

A CMDB may be populated in various ways. As discussed above, a discoveryprocedure may automatically store information related to configurationitems in the CMDB. However, a CMDB can also be populated, as a whole orin part, by manual entry, configuration files, and third-party datasources. Given that multiple data sources may be able to update the CMDBat any time, it is possible that one data source may overwrite entriesof another data source. Also, two data sources may each create slightlydifferent entries for the same configuration item, resulting in a CMDBcontaining duplicate data. When either of these occurrences takes place,they can cause the health and utility of the CMDB to be reduced.

In order to mitigate this situation, these data sources might not writeconfiguration items directly to the CMDB. Instead, they may write to anidentification and reconciliation application programming interface(API). This API may use a set of configurable identification rules thatcan be used to uniquely identify configuration items and determinewhether and how they are written to the CMDB.

In general, an identification rule specifies a set of configuration itemattributes that can be used for this unique identification.Identification rules may also have priorities so that rules with higherpriorities are considered before rules with lower priorities.Additionally, a rule may be independent, in that the rule identifiesconfiguration items independently of other configuration items.Alternatively, the rule may be dependent, in that the rule first uses ametadata rule to identify a dependent configuration item.

Metadata rules describe which other configuration items are containedwithin a particular configuration item, or the host on which aparticular configuration item is deployed. For example, a networkdirectory service configuration item may contain a domain controllerconfiguration item, while a web server application configuration itemmay be hosted on a server device configuration item.

A goal of each identification rule is to use a combination of attributesthat can unambiguously distinguish a configuration item from all otherconfiguration items, and is expected not to change during the lifetimeof the configuration item. Some possible attributes for an exampleserver device may include serial number, location, operating system,operating system version, memory capacity, and so on. If a rulespecifies attributes that do not uniquely identify the configurationitem, then multiple components may be represented as the sameconfiguration item in the CMDB. Also, if a rule specifies attributesthat change for a particular configuration item, duplicate configurationitems may be created.

Thus, when a data source provides information regarding a configurationitem to the identification and reconciliation API, the API may attemptto match the information with one or more rules. If a match is found,the configuration item is written to the CMDB. If a match is not found,the configuration item may be held for further analysis.

Configuration item reconciliation procedures may be used to ensure thatonly authoritative data sources are allowed to overwrite configurationitem data in the CMDB. This reconciliation may also be rules-based. Forinstance, a reconciliation rule may specify that a particular datasource is authoritative for a particular configuration item type and setof attributes. Then, the identification and reconciliation API will onlypermit this authoritative data source to write to the particularconfiguration item, and writes from unauthorized data sources may beprevented. Thus, the authorized data source becomes the single source oftruth regarding the particular configuration item. In some cases, anunauthorized data source may be allowed to write to a configuration itemif it is creating the configuration item or the attributes to which itis writing are empty.

Additionally, multiple data sources may be authoritative for the sameconfiguration item or attributes thereof. To avoid ambiguities, thesedata sources may be assigned precedences that are taken into accountduring the writing of configuration items. For example, a secondaryauthorized data source may be able to write to a configuration item'sattribute until a primary authorized data source writes to thisattribute. Afterward, further writes to the attribute by the secondaryauthorized data source may be prevented.

In some cases, duplicate configuration items may be automaticallydetected by reconciliation procedures or in another fashion. Theseconfiguration items may be flagged for manual de-duplication.

VI. Agent-Assisted Discovery

Disclosed herein is an approach for integrating a remote networkmanagement platform with software agent(s) deployed on device(s) of amanaged network, so as to enable agent-assisted discovery of devices,applications, and/or services on the managed network. According to thedisclosed approach, a proxy software application deployed on the managednetwork could translate (i) discovery requests from the remote networkmanagement platform into query expressions supported by a software agentand (ii) query responses from the software agent into discoveryresponses supported by the remote network management platform. The proxysoftware application could provide such translations between the remotenetwork management platform and one or more software agents of the sametype and/or of different types.

In an example implementation, the proxy software application couldreceive, from the remote network management platform, a discoveryrequest for certain information about a computing device on which asoftware agent is deployed, could translate the discovery request into aquery expression supported by the software agent, and could then providethe query expression to the software agent. The software agent may thenrespond to the query expression by transmitting, to the proxy softwareapplication, a query response including the requested information aboutthe computing device. The proxy software application could thentranslate the query response into a discovery response that is supportedby the remote network management platform and that includes theinformation at issue. In turn, the proxy software application couldprovide the discovery response to the remote network managementplatform, so that the remote network management platform can store theinformation in a CMDB and/or take other action(s).

The disclosed approach could provide for various advantages andimprovements. For example, the remote network management platform couldfacilitate agent-assisted discovery to discover configuration items thatmight not be discoverable by way of the agentless discovery describedabove in association with FIGS. 5A-5B. And by having the capability tofacilitate both agent-assisted discovery and agentless discovery, theremote network management platform could conveniently provide anenterprise with multiple options for discovering configuration items onits managed network. Moreover, because the remote network managementplatform could integrate with multiple software agents that havedifferent respective capabilities, the agent-assisted discovery couldprovide the respective benefits of each software agent without user(s)necessarily having to learn about different query expressions and/orresponses respectively supported by the different software agents. Otheradvantages are also possible.

FIG. 6 illustrates features, components, and/or operations of acomputing system 600 and of a client device 602. Although FIG. 6illustrates a specific arrangement, operations disclosed herein may becarried out in the context of similar and/or other arrangement(s) aswell without departing from the scope of the present disclosure.

The computing system 600 could include features and/or components of amanaged network and/or of a remote network management platform thatsupports remote management of the managed network.

In particular, computing system 600 may include server device(s) (notshown). The server device(s) may contain or may otherwise have access toprogram instructions executable by processor(s), so as to cause thecomputing system 600 to carry out various operations described herein.On this point, the server device(s) may include server device(s)disposed within a computational instance of a remote network managementplatform, such as within computational instance 322 of remote networkmanagement platform 320. Additionally or alternatively, the serverdevice(s) may include server device(s) disposed within the managednetwork 300 (e.g., proxy server 312). As a result, a proxy softwareapplication 604 could be deployed on such server device(s) within themanaged network 300, so as to help facilitate communication and movementof data between the managed network 300 and remote network managementplatform 320.

Further, the computing system 600 may include a database 606. Thisdatabase 606 could be a CMDB of a computational instance, such as CMDB500 for example. Additionally or alternatively, database 606 may be adatabase that is different from a CMDB. In any case, a database couldtake the form of or could otherwise be referred to herein as persistentstorage, among other possibilities.

Client device 602 may be one of the client devices 302 of the managednetwork 300, for example. Generally, the client device 702 may engage incommunication with computing system 600 (e.g., with remote networkmanagement platform 320), such as via wired and/or wirelesscommunication link(s). Moreover, as shown, the client device 702 may beconfigured to operate a web browser 608, which is an application thatmay retrieve, present, and/or navigate through information on the WorldWide Web and/or on private websites.

Furthermore, FIG. 6 depicts computing devices 610-612 on managed network300, which may be any one of the client devices 302, server devices 304,routers 306, and/or virtual machines 308 on the managed network 300. Thecomputing devices 610-612 may be respectively configured to executecertain application(s) and/or to provide certain service(s). Suchdevices, applications, and/or services may be remotely discoverable byway of agentless discovery and/or by way of agent-assisted discovery, asfurther described herein.

Yet further, FIG. 6 illustrates that a software agent 614 could bedeployed on computing device 610 and that a different software agent 616could be deployed on both computing devices 610-612. In practice, asoftware agent may be a piece of software or the like capable ofautonomously perform function(s) with respect to device(s) on which itis deployed, such as on behalf of an end user or other software. Forinstance, a software agent could receive, from an end user or othersoftware, query expression(s) that request certain information about acomputing device on which the software agent is deployed, and thesoftware agent could respond to the end user or other software withquery response(s) that include the requested information. Examples ofsoftware agents may include Osquery, Chef, and Puppet, among others.

On this point, different software agents may respectively supportdifferent query expressions and/or responses. For example, softwareagent 614 may be configured to support one set of query expressionsand/or responses and software agent 616 may be configured to support adifferent set of query expressions and/or responses. In a more specificexample, an end user or other software could request software agent 614to provide a list of active processes running on computing device 610,and could do so by transmitting, to the software agent 614, a particularquery expression having the following format: “SELECT [CPU ID],process_events”, where [CPU ID] includes an identifier of the computingdevice 610. However, the particular query expression might not besupported by software agent 616. Thus, if the end user or other softwaresubmits the same request to software agent 616, the end user or othersoftware would transmit a different query expression to software agent616, such as one having the following format: “OBTAIN process_list FROM[CPU ID]”. Other examples are also possible.

Moreover, the software agent 614, software agent 616, and agentlessdiscovery may each have respective capabilities. For example, softwareagents 614 and 616 could help obtain a list of active processes runningon a computing device 610 as described, and agentless discovery mightalso be capable of doing so. In contrast, software agent 614 could helpobtain a list of Secure Sockets Layer (SSL) certificates on thecomputing device 610, but software agent 616 and agentless discoverymight not be capable of doing so. Other examples are also possible.

According to the present disclosure, the remote network managementplatform 320 could integrate with software agent(s) deployed on themanaged network 300, so as to enable agent-assisted discovery. Tofacilitate such integration with a given software agent, the proxysoftware application 604 could authenticate the software agent, so thatthe proxy software application 604 can established secured communicationsessions with the software agent. Additionally, the proxy softwareapplication 604 could be configured to translate (i) discovery requestsfrom the remote network management platform 320 into query expressionssupported by the software agent and (ii) query responses from thesoftware agent into discovery responses supported by the remote networkmanagement platform 320.

As an initial matter, the proxy software application 604 couldauthenticate a software agent in various ways. For example, the proxysoftware application 604 and the software agent could engage incurrently-known and/or future-developed techniques of certificate-basedauthentication, such as in a TLS handshake providing mutualauthentication. Other examples are also possible.

Generally, establishing a secured communication session with a softwareagent could in and of itself assist with discovery. In particular, afterthe proxy software application 604 establishes such a session with asoftware agent, the proxy software application 604 may receive, from thesoftware agent, information indicating computing device(s) on which thesoftware agent is deployed. Based on this information, the proxysoftware application 604 may transmit, to the remote network managementplatform 320, an indication that configuration item(s) of the computingdevice(s) are discoverable by way of the software agent. If the remotenetwork management platform 320 did not previously discover thecomputing device(s), then receiving the indication may effectivelyamount to the remote network management platform 320 discovering thatthese computing device(s) are on the managed network 300.

In this way, the remote network management platform 320 couldadvantageously discover a computing device on the managed network 300regardless of how long the computing device is connected to the managednetwork 300. This type of discovery is particular beneficial, becauseagentless discovery might occur infrequently and thus might not assistwith discovering computing devices, such as laptops and mobile devices,that might connect to the managed network for shorter periods of time.Other advantages are also possible.

Further, the proxy software application 604 could be configured to carryout the above-mentioned translations in various ways. For example, theproxy software application 604 could have access to mapping data 618that enables the proxy software application 604 to carry out thetranslations. In some cases, the proxy software application 604 could beconfigured with the mapping data 618 via engineering input. In othercases, the mapping data 618 could be stored on and accessible via aserver device and/or a database of the managed network 300 and/or of theremote network management platform 320, among other options. In yetother case, the proxy software application 604 and/or the remote networkmanagement platform 320 could receive at least some of the mapping data618 from client device 602, with mapping(s) in the mapping data 618being based on input provided via a GUI displayed on the client device602.

In any case, the mapping data 618 could include query and responsemappings respectively for one or more software agents. For example,respective query mappings for software agent 614 may be between (i)formats of at least some of the discovery requests supported by theremote network management platform 320 and (ii) at least some of thequery expressions supported by software agent 614. And respectiveresponse mappings for software agent 614 may be between (i) formats ofat least some of the query responses supported by software agent 614 and(ii) at least some discovery responses supported by the remote networkmanagement platform 320. Similarly, respective query mappings forsoftware agent 616 may be between (i) formats of at least some of thediscovery requests supported by the remote network management platform320 and (ii) at least some of the query expressions supported bysoftware agent 616. And respective response mappings for software agent616 may be between (i) formats of at least some of the query responsessupported by software agent 616 and (ii) at least some discoveryresponses supported by the remote network management platform 320.

For a given software agent, its respective query mappings in the mappingdata 618 could include various discovery requests. In particular, thequery mappings may map at least some of the discovery request(s) thatthe remote network management platform 320 can use to facilitateagentless discovery. For example, the remote network management platform320 can use a particular discovery request to obtain particularinformation via agentless discovery, and that particular discoveryrequest could be mapped to a particular query expression that causes thesoftware agent to provide that particular information. Additionally oralternatively, the query mappings may map discovery request(s) otherthan those that the remote network management platform 320 can use tofacilitate agentless discovery. For example, a certain query expressioncould cause the software agent to provide certain information, but theremote network management platform 320 may not be capable of obtainingsuch information via agentless discovery. Yet, the query mappings maymap this query expression to an appropriate discovery request, so thatthe remote network management platform 320 can use this discoveryrequest to trigger agent-assisted discovery to obtain the information atissue from the software agent.

Generally, a given query mapping may associate a query expression with aformat of a discovery request in various ways. For example, the queryexpression may include predefined text string(s) and variable(s) thatare to be defined in respective locations within the query expression.Also, the associated discovery request may include predefined textstring(s) that are likely different from those of the query expression,and may also include at least some of the same variable(s) that thequery expression includes. Those variable(s) may be defined inrespective locations within the discovery request. As such, the querymapping may include respective associations between variables of thediscovery request and their corresponding variables in the queryexpression.

For example, the query mapping may associate a device identifiervariable in the query expression with a device identifier variable inthe discovery request, and may associate a file path variable in thequery expression with a file path variable in the discovery request. Inthis way, if the proxy software application 604 receives a discoveryrequest specifying a particular device identifier and a particular filepath, the proxy software application 604 could use the query mapping asbasis to generate an associated query expression that includes theparticular device identifier and the particular file path at theirrespective variable locations within the query expression.

In a more specific example, a particular discovery request may helpobtain a list of active processes running on a computing device viaagentless discovery, and that particular discovery request could bemapped to a query expression that causes a given software agent toprovide such a list. For instance, in line with the example above forsoftware agent 614, the query expression could have the followingformat: “SELECT [CPU ID], process_events”, where [CPU ID] is a variablefor a computing device identifier to be included in the queryexpression. Whereas, the discovery request could have the followingformat: “RUN Discovery on [CPU_ID], Active Processes”, where [CPU ID] issimilarly a variable for a computing device identifier to be included inthe discovery request. As such, the query mapping at issue may associatethe [CPU_ID] variable in the query expression with the [CPU_ID] variablein the discovery request.

In this regard, a given discovery request could be mapped to one queryexpression as part of respective query mappings for one software agentand could also be mapped to a different query expression as part ofrespective query mappings for a different software agent, so as tofacilitate seamless transition between use of those software agents fordiscovery. For example, referring again to the discovery request thatcan help obtain a list of active processes running on a computing devicevia agentless discovery, query mappings for software agent 614 could mapthis discovery request to the above-mentioned query expression thatcauses the software agent 614 to carry out the action at issue. Andquery mappings for software agent 616 could map this discovery requestto the above-mentioned different query expression that causes thesoftware agent 616 to carry out the same action. Other examples are alsopossible.

Further, respective response mappings for a given software agent in themapping data 618 could also take various forms. For example, thesoftware agent could be configured to provide a query response thatincludes information about a computing device in one or more datafields. A given data field may correspond to a certain attribute of thecomputing device (e.g., operating system type), such that informationincluded in that data field specifies the attribute (e.g., WINDOWS®).Therefore, a response mapping could map the given data field of thequery response to at least one of the item attributes supported by theremote network management platform 320 (e.g., to the operating systemtype attribute). Such response mappings could also be configured for anyother data field(s) of the query response, for respective data field(s)of other query response(s) supported by the software agent, and/or forrespective data field(s) of other query response(s) supported by othersoftware agent(s), among other options.

In this way, if the proxy software application 604 receives, from aparticular software agent, a query response including information in aparticular data field, the proxy software application 604 could (i)determine a particular item attribute that is mapped to the particulardata field according to response mappings for that particular agent, and(ii) generate a discovery response that associates the information inthe particular data field with the particular item attribute supportedby the remote network management platform 320. The proxy softwareapplication 604 could provide this discovery response to the remotenetwork management platform 320, and the remote network managementplatform 320 could use the discovery response as basis to store theinformation (e.g., in database 606) as the particular item attribute forthe computing device. Other examples are also possible.

Furthermore, the proxy software application 604 could have access topriority information 620 that prioritizes software agent(s) relative toone another and/or that indicates whether or not to prioritize certainsoftware agent(s) over agentless discovery. In some cases, the proxysoftware application 604 could be configured with the priorityinformation 620 via engineering input. In other cases, the priorityinformation 620 could be stored on and accessible via a server deviceand/or a database of the managed network 300 and/or of the remotenetwork management platform 320, among other options. In yet other case,the proxy software application 604 and/or the remote network managementplatform 320 could receive at least some of the priority information 620from client device 602, with one or more of the priorities in thepriority information 620 being based on input provided via a GUIdisplayed on the client device 602. In this way, a user could indicate,via the GUI, an enterprise's preferences with respect to which softwareagent should be used for discovery and/or which type of discovery shouldbe used, among other possibilities.

Given this, the proxy software application 604 could use the priorityinformation 620 to determine which software agent to use for discoveryof a computing device and/or whether to use agent-assisted discoveryrather agentless discovery of the computing device. In doing so, theproxy software application 604 could determine the type of discoverythat has the highest priority according to the priority information 620(e.g., a particular software agent) and could also determine whetherthis type of discovery is possible on the computing device. If thehighest-priority type of discovery is possible on the computing device,then the proxy software application 604 could proceed to use this typeof discovery. However, if the highest-priority type of discovery is notpossible on the computing device (e.g., if the particular software agentis not deployed on the computing device), then the proxy softwareapplication 604 could determine the type of discovery that is next inpriority according to the priority information 620 and could carry outthat type of discovery if possible, and so on.

To facilitate this, the proxy software application 604 could determinein various ways whether a certain type of discovery is possible on acomputing device. For example, the proxy software application 604 couldhave access to a list indicating which software agent(s) are deployed onwhich computing device(s) of the managed network 300.

The proxy software application 604 could access or otherwise obtain sucha list in various ways. For example, the proxy software application 604could generate such a list based on information that software agent(s)provide to indicate computing device(s) on which the software agent(s)are respectively deployed, such as following establishment of securedcommunication session(s) with those software agent(s) in line with thediscussion above. In another example, the proxy software application 604could be configured with the list via engineering input. In yet anotherexample, the list could be stored on and accessible via a server deviceand/or a database of the managed network 300 and/or of the remotenetwork management platform 320, among other options. In yet anotherexample, the proxy software application 604 and/or the remote networkmanagement platform 320 could receive the list from client device 602,the list being based on input provided via a GUI displayed on the clientdevice 602. Other examples are also possible.

Accordingly, the proxy software application 604 could use the priorityinformation 620 to select the highest-priority type of discovery that ispossible in a given discovery-related situation.

In one example situation, the proxy software application 604 couldprioritize a particular software agent over other software agent(s)and/or over agentless discovery. For example, the proxy softwareapplication 604 could receive, from the remote network managementplatform 320, a discovery request that requests information related tocomputing device 610. In turn, the proxy software application 604 coulddetermine (i) that the priority information 620 prioritizes the softwareagent 614 over software agent 616 as well as over agentless discoveryand (ii) that the software agent 614 is deployed on the computing device610. Based on this determination, the proxy software application 604could determine that the discovery request is to be performed by way ofthe software agent 614 rather than by way of software agent 616 and/orby way of agentless discovery.

In another example situation, the proxy software application 604 coulduse a lower-priority software agent over a higher-priority softwareagent if the higher-priority software agent is not deployed on atargeted computing device. For example, the proxy software application604 could receive, from the remote network management platform 320, adiscovery request that requests information related to computing device612. In turn, the proxy software application 604 could determine thatthe priority information 620 prioritizes the software agent 614 oversoftware agent 616, but may also determine that software agent 614 isnot deployed on computing device 612. Responsive to determining thatsoftware agent 614 is not deployed on computing device 612 and based onsoftware agent 616 being deployed on computing device 612 and being nextin priority according to priority information 620, the proxy softwareapplication 604 could determine that the discovery request is to beperformed by way of software agent 616.

In yet another example situation, the proxy software application 604could use agentless discovery over software agent(s) that are of higherpriority compared to agentless discovery, such as when the softwareagent(s) are not deployed on a targeted computing device. For example,the proxy software application 604 could receive, from the remotenetwork management platform 320, a discovery request that requestsinformation related to a particular computing device. In turn, the proxysoftware application 604 could determine that the priority information620 prioritizes one or more software agent(s) over agentless discovery,but may also determine that none of those software agent(s) are deployedon the computing device. Responsive to determining that none of thesoftware agent(s) are deployed on the computing device and based onagentless discovery being next in priority after the software agent(s)according to the priority information 620, the proxy softwareapplication 604 could determine that the discovery request is to beperformed by way of agentless discovery. Other examples situations arealso possible.

In a system arranged as described above, the proxy software application604 could engage in agent-assisted discovery in response to receiving adiscovery request 622 from the remote network management platform 320(or more specifically from computational instance 322). The proxysoftware application 604 could receive such a discovery request 622 invarious ways. For example, the remote network management platform 320could transmit discovery request(s) to the proxy software application604 according to a schedule, which may be a predefined schedule or maybe a schedule established based on input provided via client device 602,among other options. In another example, a task list on computationalinstance 322 (e.g., task list 502) may be populated (e.g., according toinput provided via client device 602) with task(s) that correspond todiscovery request(s), and proxy software application 604 could query thetask list to obtain a task corresponding to a given discovery request.

Once the proxy software application 604 receives the discovery request622, the proxy software application 604 could determine that thediscovery request 622 targets a particular computing device and is to beperformed by a particular software agent. For example, the discoveryrequest 622 could programmatically specify a request for particularinformation about computing device 610, and the proxy softwareapplication 604 could thus read the discovery request 622 to determinethat the computing device 610 is being targeted by the discovery request622. Moreover, the proxy software application 604 could determine thatthe discovery request 622 is to be performed by software agent 614according to priority information 620 and based on a determination thatsoftware agent 614 is deployed on the computing device 610, in line withthe discussion above.

Subsequently, the proxy software application 604 could engage inagent-assisted discovery using the software agent 614 determined toperform the discovery request 622. In this process, the proxy softwareapplication 604 could use the discovery request 622 as basis togenerate, by way of respective query mappings in mapping data 618 forsoftware agent 614, a query expression 624 supported by software agent614, and do so as described herein. The proxy software application 604could then transmit the generated query expression 624 to the softwareagent 614 and could receive, from the software agent 614, a queryresponse 626 specifying the requested information 628 related to thecomputing device 610. In turn, the proxy software application 604 coulduse the query response 626 as basis to generate, by way of respectiveresponse mappings in the mapping data 618 for software agent 614, adiscovery response 630 supported by the remote network managementplatform 320, and do so as described herein. This discovery response 630may represent information 632, which may include some or all of theinformation 628 from the query response 626 and/or may include amodified version of at least some of the information 628, among otheroptions.

On this point, generating a discovery response could sometimes involvefile format conversion. For example, a query response from a softwareagent might be included within or may otherwise take the form ofJavaScript Object Notation (JSON) file(s), XML file(s), or other type(s)of text file(s), among other options. However, remote network managementplatform 320 might not support the file format of the query response,and thus proxy software application 604 could generate the discoveryresponse to have a file format supported by the remote networkmanagement platform 320. In practice, this may involve the proxysoftware application 604 using currently known and/or future-developedtechniques to convert an obtained query response having a certain fileformat (e.g., JSON) to a discovery response having another format (e.g.,XML). Other examples are also possible.

In any case, after the proxy software application 604 generates thediscovery response 630, the proxy software application 604 couldtransmit the discovery response 630 to the remote network managementplatform 320. Once the remote network management platform 320 receivesthe discovery response 630, the remote network management platform 320could take one or more actions. For example, the remote networkmanagement platform 320 could store, in database 606, the information632 related to computing device 610 as configuration item(s).Additionally or alternatively, the remote network management platform320 could transmit the information 632 to client device 602, so thatclient device 602 could display the information 632 via browser 608, forexample. Other examples are also possible.

According to the present disclosure, the proxy software application 604could engage in agent-assisted discovery using one or more softwareagents. For example, the proxy software application 604 could engage inagent-assisted discovery using software agent 614 as described above,and could also engage in agent-assisted discovery using software agent616.

For example, the proxy software application 604 could receive adifferent discovery request that targets computing device 612, and coulddetermine that the different discovery request is to be performed by wayof software agent 614. The proxy software application 604 could use thedifferent discovery request as basis to generate, by way of respectivequery mappings in mapping data 618 for software agent 616, a differentquery expression supported by software agent 616. The proxy softwareapplication 604 could then transmit this generated query expression tothe software agent 616 and could receive, from the software agent 616, aquery response specifying the requested information related to thecomputing device 612. In turn, the proxy software application 604 coulduse this query response as basis to generate, by way of respectiveresponse mappings in the mapping data 618 for software agent 616, adiscovery response supported by the remote network management platform320, which may represent the information from the query response. Theproxy software application 604 could then transmit this discoveryresponse to the remote network management platform 320. Other examplesare also possible.

In some implementations, an entity other than proxy software application604 could carry out the above-described translation(s) and/orprioritization. For example, the remote network management platform 320(or more specifically computational instance 322) could have access tothe mapping data 618 and could thus carry the translation(s). In thisprocess, the remote network management platform 320 could determine thata discovery request targets a particular computing device and is to beperformed by a particular software agent. Given this, the remote networkmanagement platform 320 could use the discovery request as basis togenerate, by way of mapping data 618, a query expression supported bythe software agent, and could then transmit the query expression to theproxy software application 604. The proxy software application 604 couldprovide the query expression to the software agent, could receive aquery response from the software agent, and could transmit the queryresponse to the remote network management platform 320. The remotenetwork management platform 320 could then use the query response asbasis to generate, by way of mapping data 618, a discovery responsesupported by the remote network management platform 320, and could thenstore, in database 322, information included in the discovery responseand/or carry out other action(s). Other implementations are alsopossible.

In a further aspect, the present disclosure also provides for a GUI thatenables submission of request(s) for information to software agent(s)via a client device (e.g., client device 602). The GUI could includeinterface element(s) for specifying such request(s). In one case, theinterface element(s) could enable submission of a query expressionsupported by a given software agent, so as to request certaininformation about a computing device from the software agent. In anothercase, the interface element(s) could enable submission of a discoveryrequest for certain information about a computing device, which could beperformed by a software agent. For example, a user could select thedesired information from a drop-down menu in the GUI, could enterrespective identifiers of computing device(s) into field(s) of the GUI,and could optionally select a software agent to perform discovery, so asto trigger a discovery request for the information about the computingdevice(s).

In any case, the remote network management platform 320 could facilitatediscovery in various ways according to the request(s) submitted via theGUI, so as to then provide the requested information for display via theGUI.

For example, the remote network management platform 320 could provide,to the client device 602 a representation of the GUI that includesinterface elements for specifying query expression(s) supported bysoftware agent(s). In turn, the remote network management platform 320could receive, from the client device 602 and by way of the GUI, aparticular query expression supported by a particular software agent,and the remote network management platform 320 could transmit the queryexpression to the proxy software application 604. The proxy softwareapplication 604 could then bypass the mapping data 618 (or morespecifically the query mappings for the software agent) and transmit thequery expression to the software agent. The software agent could providea query response to the proxy software application 604, and the proxysoftware application 604 could bypass the mapping data 618 (or morespecifically the response mappings for the particular software agent)and transmit the query response to the remote network managementplatform 320. The remote network management platform 320 could thenprovide, to the client device 602, an updated representation of the GUIthat displays a version of the query response.

In another example, the remote network management platform 320 couldprovide, to the client device 602 a representation of the GUI thatincludes interface elements for specifying discovery request(s). Inturn, the remote network management platform 320 could receive, from theclient device 602 and by way of the GUI, a discovery request forinformation about a certain computing device, and the remote networkmanagement platform 320 could transmit the discovery request to theproxy software application 604. The proxy software application 604 coulddetermine that the discovery request is to be performed by a particularsoftware agent, could translate the discovery request into a queryexpression supported by that software agent, and could transmit thequery expression to the software agent. The software agent may respondto the query expression by providing a query response including therequested information to the proxy software application 604. The proxysoftware application 604 could then translate the query response into adiscovery response that includes the information and that is supportedby the remote network management platform 320, and could then providethe discovery response to the remote network management platform 320.The remote network management platform 320 could then provide, to theclient device 602, an updated representation of the GUI that displays aversion of the discovery response. Other examples are also possible.

In this way, an enterprise could use the GUI to submit request(s) forinformation to software agent(s) via the remote network managementplatform 320. User(s) could submit such request(s) at any time and couldreceive requested information substantially in real-time. This may beparticularly beneficial when user(s) urgently need to obtain certaininformation about computing device(s), such as when IT professionalsattempt to remediate urgent issues encountered by the computingdevice(s), among other possibilities.

VII. Example Operations

FIG. 7 is a flow chart illustrating an example embodiment. The processillustrated by FIG. 7 may be carried out by a computing system, such ascomputing device 100, and/or a cluster of computing devices, such asserver cluster 200. However, the process can be carried out by othertypes of devices or device subsystems. For example, the process could becarried out by a portable computer, such as a laptop or a tablet device.

The embodiments of FIG. 7 may be simplified by the removal of any one ormore of the features shown therein. Further, these embodiments may becombined with features, aspects, and/or implementations of any of theprevious figures or otherwise described herein.

Block 700 may involve receiving, by a proxy software application from aremote network management platform, a discovery request, where theremote network management platform is associated with a managed network,where persistent storage is disposed within a remote network managementplatform, where the persistent storage contains representations ofdiscovered configuration items within the managed network, where asoftware agent is deployed on a computing device of the managed networkand configured to respond to query expressions with query responsesspecifying configurations of the computing device, where the proxysoftware application is disposed within the managed network, and wherethe proxy software application (i) is configured to cause discovery ofconfiguration items on the computing device in response to receivingdiscovery requests from the remote network management platform, (ii) hasaccess to query mappings between formats of at least some of thediscovery requests and at least some of the query expressions, and (iii)has access to response mappings between formats of at least some of thequery responses and at least some discovery responses supported by theremote network management platform.

Block 702 may involve determining, by the proxy software application,that the discovery request targets the computing device and is to beperformed by way of the software agent.

Block 704 may involve, based on the discovery request, generating, bythe proxy software application and using the query mappings, a queryexpression.

Block 706 may involve transmitting, by the proxy software application tothe software agent, the query expression.

Block 708 may involve receiving, by the proxy software application fromthe software agent, a query response specifying configurationinformation related to the computing device.

Block 710 may involve generating, by the proxy software application andusing the response mappings, a discovery response representing theconfiguration information related to the computing device.

Block 712 may involve transmitting, by the proxy software application tothe remote network management platform, the discovery response.

In some embodiments, the remote network management platform may beconfigured to: receive, from the proxy software application, thediscovery response; and store, in the persistent storage, theconfiguration information related to the computing device asconfiguration items.

In some embodiments, a different software agent may also be deployed onthe computing device, the proxy software application may have access topriority information that prioritizes the software agent over thedifferent software agent, and the proxy software application may use thepriority information as basis to determine that the discovery request isto be performed by way of the software agent rather than by way of thedifferent software agent.

In some embodiments, a different software agent may be deployed on oneor more other computing devices of the managed network, the the proxysoftware application may have access to priority information indicatingthat the software agent is next in priority after the different softwareagent, thereby prioritizing the different software agent over thesoftware agent. In such embodiments, (i) the proxy software applicationmay be further configured to determine that the different software agentis not deployed on the computing device, and (ii) determining that thediscovery request is to be performed by way of the software agent mayinvolve determining, in response to determining that the differentsoftware agent is not deployed on the computing device and based on thethe software agent being next in priority according to the priorityinformation, that the discovery request is to be performed by way of thesoftware agent rather than by way of the different software agent.

In some embodiments, the proxy software application may have access topriority information indicating that agentless discovery is next inpriority after the software agent, thereby prioritizing the softwareagent over the agentless discovery, and the proxy software applicationmay be further configured to: receive, from the remote networkmanagement platform, a different discovery request that targets adifferent computing device; determine that the software agent is notdeployed on the different computing device; in response to determiningthat the software agent is not deployed on the different computingdevice and based on the agentless discovery being next in priorityaccording to the priority information, determine that the differentdiscovery request is to be performed by way of the agentless discoveryrather than by way of the software agent; and engage in the agentlessdiscovery of configuration items on the different computing device inresponse to receiving the different discovery request.

In some embodiments, a different software agent may also be deployed onthe computing device and may be configured to respond to different queryexpressions with different query responses specifying configurations ofthe computing device. Additionally, the proxy software application mayalso (i) have access to different query mappings between formats of atleast some of the discovery requests and at least some of the differentquery expressions, and (ii) have access to different response mappingsbetween formats of at least some of the different query responses and atleast some of the discovery responses supported by the remote networkmanagement platform.

In such embodiments, the proxy software application may be furtherconfigured to: receive, from the remote network management platform, adifferent discovery request, where the different discovery request isalso for the configuration information related to the computing device;determine that the different discovery request targets the computingdevice and is to be performed by way of the different software agentrather than by way of the software agent; based on the differentdiscovery request, generate, by way of the different query mappings, adifferent query expression; transmit, to the different software agent,the different query expression; receive, from the different softwareagent, a different query response specifying the configurationinformation related to the computing device; and generate, based on thedifferent query response and by way of the different response mappings,a different discovery response representing the configurationinformation related to the computing device.

In some embodiments, the proxy software application may be furtherconfigured to: establish a secured communication session with thesoftware agent; after establishing the secured communication session,receive, from the software agent, information indicating that thesoftware agent is deployed on the computing device; and based on theinformation indicating that the software agent is deployed on thecomputing device, transmit, to the remote network management platform,an indication that configuration items of the computing device arediscoverable by way of the software agent.

In some embodiments, the proxy software application may be furtherconfigured to: receive, from the remote network management platform, aparticular query expression from among the query expressions supportedby the software agent; bypass the query mappings and transmit, to thesoftware agent, the particular query expression received from the remotenetwork management platform; in response to transmitting the particularquery expression, receive, from the software agent, a particular queryresponse; and bypass the response mappings and transmit, to the remotenetwork management platform, the particular query response.

In such embodiments, the remote network management platform may beconfigured to: provide, to a client device associated with the managednetwork, a representation of a GUI that includes interface elements forspecifying one or more of the query expressions supported by thesoftware agent; receive, from the client device and by way of the GUI,the particular query expression; transmit, to the proxy softwareapplication, the particular query expression; receive, from the proxysoftware application, the particular query response; and provide, to theclient device, an updated representation of the GUI that displays aversion of the particular query response.

VIII. Conclusion

The present disclosure is not to be limited in terms of the particularembodiments described in this application, which are intended asillustrations of various aspects. Many modifications and variations canbe made without departing from its scope, as will be apparent to thoseskilled in the art. Functionally equivalent methods and apparatuseswithin the scope of the disclosure, in addition to those describedherein, will be apparent to those skilled in the art from the foregoingdescriptions. Such modifications and variations are intended to fallwithin the scope of the appended claims.

The above detailed description describes various features and operationsof the disclosed systems, devices, and methods with reference to theaccompanying figures. The example embodiments described herein and inthe figures are not meant to be limiting. Other embodiments can beutilized, and other changes can be made, without departing from thescope of the subject matter presented herein. It will be readilyunderstood that the aspects of the present disclosure, as generallydescribed herein, and illustrated in the figures, can be arranged,substituted, combined, separated, and designed in a wide variety ofdifferent configurations.

With respect to any or all of the message flow diagrams, scenarios, andflow charts in the figures and as discussed herein, each step, block,and/or communication can represent a processing of information and/or atransmission of information in accordance with example embodiments.Alternative embodiments are included within the scope of these exampleembodiments. In these alternative embodiments, for example, operationsdescribed as steps, blocks, transmissions, communications, requests,responses, and/or messages can be executed out of order from that shownor discussed, including substantially concurrently or in reverse order,depending on the functionality involved. Further, more or fewer blocksand/or operations can be used with any of the message flow diagrams,scenarios, and flow charts discussed herein, and these message flowdiagrams, scenarios, and flow charts can be combined with one another,in part or in whole.

A step or block that represents a processing of information cancorrespond to circuitry that can be configured to perform the specificlogical functions of a herein-described method or technique.Alternatively or additionally, a step or block that represents aprocessing of information can correspond to a module, a segment, or aportion of program code (including related data). The program code caninclude one or more instructions executable by a processor forimplementing specific logical operations or actions in the method ortechnique. The program code and/or related data can be stored on anytype of computer readable medium such as a storage device including RAM,a disk drive, a solid state drive, or another storage medium.

The computer readable medium can also include non-transitory computerreadable media such as computer readable media that store data for shortperiods of time like register memory and processor cache. The computerreadable media can further include non-transitory computer readablemedia that store program code and/or data for longer periods of time.Thus, the computer readable media may include secondary or persistentlong term storage, like ROM, optical or magnetic disks, solid statedrives, compact-disc read only memory (CD-ROM), for example. Thecomputer readable media can also be any other volatile or non-volatilestorage systems. A computer readable medium can be considered a computerreadable storage medium, for example, or a tangible storage device.

Moreover, a step or block that represents one or more informationtransmissions can correspond to information transmissions betweensoftware and/or hardware modules in the same physical device. However,other information transmissions can be between software modules and/orhardware modules in different physical devices.

The particular arrangements shown in the figures should not be viewed aslimiting. It should be understood that other embodiments can includemore or less of each element shown in a given figure. Further, some ofthe illustrated elements can be combined or omitted. Yet further, anexample embodiment can include elements that are not illustrated in thefigures.

While various aspects and embodiments have been disclosed herein, otheraspects and embodiments will be apparent to those skilled in the art.The various aspects and embodiments disclosed herein are for purpose ofillustration and are not intended to be limiting, with the true scopebeing indicated by the following claims.

What is claimed is:
 1. A system, comprising: one or more hardwareprocessors; and a non-transitory memory storing instructions that, whenexecuted by the one or more hardware processors, causes the one or morehardware processors to perform actions comprising: receiving a discoveryrequest to discover configuration items of a managed network, whereinthe discovery request is in a first request format supported by a remotenetwork management platform; generating a query expression based on thediscovery request, wherein the query expression is in a second requestformat supported by a software agent deployed on a computing device;transmitting the query expression to the software agent; receiving aquery response comprising configuration information of the computingdevice from the software agent, wherein the query response is in a firstresponse format supported by the software agent; generating a discoveryresponse comprising the configuration information based on the queryresponse, wherein the query response is in a second response formatsupported by the remote network management platform; and transmittingthe discovery response to the remote network management platform.
 2. Thesystem of claim 1, wherein the actions comprise: determining that thediscovery request targets the computing device; and in response todetermining that the discovery request targets the computing device,generating the query expression and transmitting the query expression tothe software agent deployed on the computing device.
 3. The system ofclaim 1, wherein the actions comprise, prior to transmitting the queryexpression, authenticating the software agent via certificate-basedauthentication.
 4. The system of claim 1, wherein the discovery requestcomprises a request to discover the configuration items via agentlessdiscovery, and wherein the actions comprise mapping the discoveryrequest to the software agent configured to discover the configurationitems.
 5. The system of claim 4, wherein the discovery request comprisesan identifier of the computing device and a request to identify activeprocesses running on the computing device, and wherein mapping thediscovery request to the software agent comprises identifying thesoftware agent deployed on the computing device and configured toprovide a list of the active processes.
 6. The system of claim 1,wherein the actions comprise: determining that the discovery requestapplies to a plurality of software agents deployed on the computingdevice, wherein the plurality of software agents comprise the softwareagent and an additional software agent; generating an additional queryexpression based on the discovery request, wherein the additional queryexpression is in an additional request format supported by theadditional software agent; and transmitting the additional queryexpression to the additional software agent.
 7. The system of claim 1,wherein the configuration information of the computing device comprisesa data field corresponding to an attribute of the computing device, andwherein generating the discovery response comprising the configurationinformation comprises mapping the data field to at least one itemattribute supported by the remote network management platform.
 8. Thesystem of claim 1, wherein the actions comprise determining that thediscovery request is to be performed by the software agent based on afirst priority of the software agent being greater than a secondpriority of agentless discovery.
 9. The system of claim 1, wherein theactions comprise determining that discovery is to be performed by thesoftware agent based on a first priority of the software agent beinggreater than a second priority of an additional software agent.
 10. Amethod, comprising: receiving a discovery request to discoverconfiguration items of a managed network, wherein the discovery requestis in a first request format supported by a remote network managementplatform; generating a query expression based on the discovery request,wherein the query expression is in a second request format supported bya software agent deployed on a computing device; transmitting the queryexpression to the software agent; receiving a query response comprisingconfiguration information of the computing device from the softwareagent, wherein the query response is in a first response formatsupported by the software agent; generating a discovery responsecomprising the configuration information based on the query response,wherein the query response is in a second response format supported bythe remote network management platform; and transmitting the discoveryresponse to the remote network management platform.
 11. The method ofclaim 10, wherein the discovery request comprises a request to discoverthe configuration items via agentless discovery, and comprising mappingthe discovery request to the software agent configured to discover theconfiguration items.
 12. The method of claim 11, wherein the discoveryrequest comprises an identifier of the computing device and a request toidentify active processes running on the computing device, and whereinmapping the discovery request to the software agent comprisesidentifying the software agent deployed on the computing device andconfigured to provide a list of the active processes.
 13. The method ofclaim 10, comprising: determining that the discovery request applies toa plurality of software agents deployed on the computing device, whereinthe plurality of software agents comprise the software agent and anadditional software agent; generating an additional query expressionbased on the discovery request, wherein the additional query expressionis in an additional request format supported by the additional softwareagent; and transmitting the additional query expression to theadditional software agent.
 14. The method of claim 10, comprisingdetermining that discovery is to be performed by the software agentbased on a first priority of the software agent being greater than asecond priority of an additional software agent.
 15. A non-transitorycomputer-readable medium comprising computer readable code, that whenexecuted by one or more processors, causes the one or more processors toperform operations comprising: receiving a discovery request to discoverconfiguration items of a managed network, wherein the discovery requestis in a first request format supported by a remote network managementplatform; generating a query expression based on the discovery request,wherein the query expression is in a second request format supported bya software agent deployed on a computing device; transmitting the queryexpression to the software agent; receiving a query response comprisingconfiguration information of the computing device from the softwareagent, wherein the query response is in a first response formatsupported by the software agent; generating a discovery responsecomprising the configuration information based on the query response,wherein the query response is in a second response format supported bythe remote network management platform; and transmitting the discoveryresponse to the remote network management platform.
 16. Thenon-transitory computer-readable medium of claim 15, wherein theoperations comprise mapping the discovery request to the software agentconfigured to discover the configuration items.
 17. The non-transitorycomputer-readable medium of claim 16, wherein the discovery requestcomprises an identifier of the computing device and a request toidentify active processes running on the computing device, and whereinmapping the discovery request to the software agent comprisesidentifying the software agent deployed on the computing device andconfigured to provide a list of the active processes.
 18. Thenon-transitory computer-readable medium of claim 15, wherein theoperations comprise, prior to transmitting the query expression,authenticating the software agent via certificate-based authentication.19. The non-transitory computer-readable medium of claim 15, wherein theconfiguration information of the computing device comprises a data fieldcorresponding to an attribute of the computing device, and whereingenerating the discovery response comprising the configurationinformation comprises mapping the data field to at least one itemattribute supported by the remote network management platform.
 20. Thenon-transitory computer-readable medium of claim 15, wherein theoperations comprise determining that discovery is to be performed by thesoftware agent based on a first priority of the software agent beinggreater than a second priority of agentless discovery.